Click or drag to resize
Double-Take Cmdlets Summary

Double-Take includes Windows PowerShell cmdlets that you can use to control most Double-Take features. This guide includes all of the Double-Take cmdlets available. However, this guide does not explain how to use Windows PowerShell. You should reference your Windows PowerShell documentation and the many web sites devoted to PowerShell to learn how to use and script with Windows PowerShell.

The following terms and definitions will help you understand Double-Take basics. See the User's Guide for your Double-Take product for complete details on how that product works.

  • Source—The source is the server that has the data you want to protect or migrate. Typically this is a machine on the production network that serves data to clients.

  • Target—The target is the server that maintains the replicated copy of the data that is being protected on the source. Typically this is a backup server that may be local or in a remote data center. For migration jobs, this is the final destination for your data.

  • Workload—A workload is a logical definition of the data that is being protected or migrated on the source. A workload can be a simple set of paths, for example, C:\Data or /usr. It may also be a more complex logical item that maps to multiple paths. For example, protecting a virtual machine means you are protecting multiple, specific virtual machine files, or protecting Microsoft SQL means you are protecting a SQL database and its related files.

  • Workload manager—The workload manager is a web service that creates and configures the Double-Take workload.

  • Job—A job is a logical unit that includes the source, target, and the workload. The job is what you create and monitor in order to protect or migrate your data.

  • Job manager—The job manager is a web service that creates, monitors, and controls the Double-Take job.

  • Connection—The engine connection is the underlying stream that sends the actual replicated data between the source and target servers. Jobs are higher-level objects that use the lower-level connection to protect data.

  • Architecture—Each Double-Take installation has two services, the Management Service and Engine.

    • Management Service—This service is displayed as Double-Take Management Service in the Windows services list and jsvc on Linux. The service hosts the job manager and provides monitoring and control for all job types. For WCF clients, the service listens on port 6325. For non-WCF clients, the service listens on port 6326. This service offers a SOAP-based XML web services interface.

    • Engine—This service is displayed as Double-Take in the Windows service list and DT on Linux. The service transmits the replicated data between the source and target servers. By default this service listens on port 6320. You do not interact directly with this service.

  • Roles—Any Double-Take installation can be a source, target, or both. The existence of a job between two servers and which direction data is being transmitted determines the server’s role.

  • Security—Double-Take enforces security by using local groups on each server where Double-Take is installed. There are two levels of security. Administrator access allows full control of Double-Take on a server, and monitor access allows read-only views of job information. When you connect to the job manager on a server, you will need to provide the credentials of a user who is a member of one of the local groups on that server.

  • Job creation—To create a job, you will first communicate with the source to create a workload. You will then use that workload object and communicate with the target to create the job.

  • Monitoring and controlling jobs—To monitor and control jobs, you will communicate with the job manager on the target of the job.